This pull request introduces a new configuration option, serverTelemetryEnabled, to the MSAL Browser library, allowing developers to enable or disable server telemetry headers and caching of failed requests. The option is added with a default value of false and is marked as deprecated for future removal. The PR updates the configuration logic, documentation, and all interaction clients to respect this flag, and adds tests to verify correct behavior.

Configuration and API changes:

• Added the serverTelemetryEnabled option to BrowserSystemOptions in both the API and implementation, with a default value of false and marked as deprecated for future removal. This controls whether MSER server telemetry headers are sent and failed requests are cached. [1] [2] [3]

• Updated the documentation (configuration.md) to describe the new serverTelemetryEnabled option, its default value, and its effect. Also updated example configuration usage. [1] [2]

Code updates for telemetry behavior:

• Modified the initializeServerTelemetryManager function to accept an enabled parameter, defaulting to true, and return a stub manager when telemetry is disabled. Updated all interaction clients (PopupClient, RedirectClient, SilentAuthCodeClient, SilentCacheClient, SilentIframeClient, SilentRefreshClient, PlatformAuthInteractionClient) to pass the new flag from configuration. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18]

Testing and validation:

• Added and updated unit tests to verify the default value of serverTelemetryEnabled, its behavior when set to true, and that telemetry data is written to storage only when enabled. [1] [2] [3] [4]

API review and type updates:

• Updated API review files and error comments to reflect the changes in configuration and internal types.

Configuration changes:

• Added serverTelemetryEnabled (default false, deprecated) to BrowserSystemOptions and configuration builder, controlling whether server telemetry headers are sent and failed requests are cached. [1] [2] [3]
• Updated documentation and example usage to include and explain serverTelemetryEnabled. [1] [2]

Telemetry manager updates:

• Updated initializeServerTelemetryManager to support disabling telemetry, returning a stub manager when disabled; all interaction clients now respect this configuration flag. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18]

Testing:

• Added and updated unit tests to verify default and explicit values of serverTelemetryEnabled, and that telemetry is written to storage only when enabled. [1] [2] [3] [4]

API review:

• Updated API review files and comments to reflect new configuration and type changes.